1
00:00:01,370 --> 00:00:11,570
That we create a machine we need to give IT resources in order to run our Sebille memory story and all

2
00:00:11,570 --> 00:00:14,220
other parts of our computer.

3
00:00:14,880 --> 00:00:22,360
That an operating system relies on and to give the resources to our guest machine.

4
00:00:22,780 --> 00:00:31,150
We need to bake or otherwise designate resources on the host your whole system has one or more Scipio's

5
00:00:31,230 --> 00:00:39,790
on processors that take care of running software and doing the math that makes almost everything on

6
00:00:39,790 --> 00:00:41,320
the system work.

7
00:00:41,670 --> 00:00:49,200
But we create a virtual machine we need to tell what toolbox home and the processor the guest operating

8
00:00:49,200 --> 00:00:52,400
system has to do.

9
00:00:52,500 --> 00:00:58,600
This does not need to exactly match what the whole system has.

10
00:00:58,610 --> 00:01:04,830
In fact it's usually a good idea to give the guest fewer places than the host has.

11
00:01:05,880 --> 00:01:13,530
Telling a guest that it has set the number up to secert does roadblock or persists from the rest of

12
00:01:13,530 --> 00:01:14,570
the system.

13
00:01:16,190 --> 00:01:22,440
The virtual box that we're scared of sending commands from the guest to the processor as they need to

14
00:01:22,440 --> 00:01:33,600
be executed on an older horse that don't support what Tula's Ishan box will Mullett possessor.

15
00:01:33,660 --> 00:01:41,880
Instead it will appear to the first operating system that it has given amount of persisting resources.

16
00:01:43,100 --> 00:01:47,430
Though that's not strictly strictly true.

17
00:01:47,470 --> 00:01:54,960
It's really competing with the host and other guest for the time running instructions on the process.

18
00:01:55,740 --> 00:02:05,320
Typically you can get by just fine with one processor but if you are a guest will be doing more combinational

19
00:02:05,430 --> 00:02:09,340
interesting things you can add more processor.

20
00:02:09,360 --> 00:02:10,730
If they are available

21
00:02:13,290 --> 00:02:21,450
allocating memory to against them all the memory against CVS but the memory is not taken up all at once

22
00:02:21,510 --> 00:02:28,410
on the host get started using them the host memory gets taken up.

23
00:02:28,450 --> 00:02:36,680
And as things go out of memory on our guest the host of memory is released as well.

24
00:02:36,910 --> 00:02:44,020
So the number that we set for the memory I guess to the present the large amount of memory that it can

25
00:02:44,020 --> 00:02:52,570
take on the host most of the time guest needs storage in order to install them running the system or

26
00:02:52,720 --> 00:02:58,260
work with data you really it will create a virtual hard drive.

27
00:02:59,380 --> 00:03:03,930
As a file on the host and for that we have two options.

28
00:03:05,280 --> 00:03:06,210
Two options.

29
00:03:06,220 --> 00:03:14,250
We can create a dynamic image on a fixed image file both title file provides a hard disk Unforgiven

30
00:03:14,380 --> 00:03:17,730
size to a great guest operating system.

31
00:03:17,920 --> 00:03:27,620
And the difference lies in hold the file is managed on the host or that image only takes up space on

32
00:03:27,620 --> 00:03:37,040
the host as data is added to it and a fixed image file takes all of the space for the guest hard drive

33
00:03:37,580 --> 00:03:39,760
right from the beginning.

34
00:03:39,830 --> 00:03:44,720
Reading and writing data from the fix we need is a little bit faster.

35
00:03:44,990 --> 00:03:50,540
But to fix the image takes up a lot of space but it helps you to

36
00:03:54,450 --> 00:03:58,210
conserve space on the host.

37
00:03:58,230 --> 00:04:07,170
It does not take up tens or hundreds of gigabyte to store a mostly empty guest hard drive for networking.

38
00:04:08,380 --> 00:04:17,980
Video Audio and chipset virtual boss creates a series of emulated devices devices which looks to the

39
00:04:17,980 --> 00:04:24,890
guest as though they are real devices but which in reality are virtual.

40
00:04:26,110 --> 00:04:33,430
What you want takes the information sent to these little devices and translates it to the host computer.

41
00:04:35,240 --> 00:04:36,120
Real hard.

42
00:04:36,170 --> 00:04:43,170
How did the devices are pretty generic and most of us just don't have built in support for them.

43
00:04:44,310 --> 00:04:51,070
Usually we don't need special drivers or anything to get them working on a common labelling system.

44
00:04:53,910 --> 00:04:55,490
As you will see later on.

45
00:04:55,530 --> 00:04:59,450
A big exception here is the video device.

46
00:04:59,790 --> 00:05:08,310
The vulnerable toolbar use a very generic device and many object system like a fallback or the lowest

47
00:05:08,310 --> 00:05:10,990
common denominator.

48
00:05:11,220 --> 00:05:17,690
So we need to install a driver with a guest and the Shanes in order to get a better experience.

49
00:05:18,760 --> 00:05:22,140
More reservation's options and so on.

50
00:05:22,160 --> 00:05:25,140
I look at the resources between the host and Gerster machine.

51
00:05:25,150 --> 00:05:34,730
Is all these are Bello's you need to make sure you give your guests enough resources but not at the

52
00:05:34,730 --> 00:05:39,950
expense of the host usability or stability.

53
00:05:39,950 --> 00:05:49,000
Taking too much processor time are limited and can slow down the host to the point of load running very

54
00:05:49,000 --> 00:05:55,570
well and piggin too much disk space can cause problem when the host needs to see files.

55
00:05:55,580 --> 00:05:56,330
Two days.
